Tuned display positions and text for screw levels (n4max)#59
Merged
halfmanbear merged 1 commit intoOpenNeptune3D:devfrom Feb 25, 2026
Merged
Tuned display positions and text for screw levels (n4max)#59halfmanbear merged 1 commit intoOpenNeptune3D:devfrom
halfmanbear merged 1 commit intoOpenNeptune3D:devfrom
Conversation
halfmanbear
added a commit
that referenced
this pull request
Feb 25, 2026
* Add PAGE_PRINTING_KAMP to PRINTING_PAGES list * Implement rapid scan mode for bed leveling Added rapid scan mode functionality to improve bed leveling process. * Refactor rapid scan mode handling in display.py * Refactor bed leveling completion handling * Enhance rapid scan mode detection in display.py * Enhance response check for bed leveling completion * Fix G-code response handling for probe messages * Enhance affinity setup with multiprocessing detection Added auto-detection for multiprocessing plugins and enhanced logging for IRQs and multiprocessing support. * Refactor affinity-setup.sh for improved performance Enhance affinity setup script with improved error handling, faster polling, and better CPU validation. Update child process management and logging for multiprocessing plugins. * Update affinity-setup.sh Refactor & simplified affinity setup script for low-jitter tuning and more relaxed CPU management. * Refactor kamp page display logic and cleanup conditions * Improve file locking and error handling Refactor file locking and error handling in display.py for better concurrency and reliability. * Make display updates self-apply and simplify affinity tuning * Harden display async lifecycle and prevent page/thumbnail write races * Add auto_unblock parameter to write assertion * Simplify pending request cancellation on close Refactor closing logic to simplify pending request handling. * Refactor display positions and text for screw levels (#59) --------- Co-authored-by: LinFor <linfor@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I corrected the coordinates of the blocks, because the text is not displayed correctly on n4max (it is overlapped by the retry button).
In addition, the coordinates of the text hints (CL, CR) were mixed up for n4max, they were not in their places (FL, CL, respectively).
I did not touch the coordinates of the non-n4max blocks (FR, FL, RR, RL), I only brought the formatting of the code to a uniform one. Although it is possible that they should be aligned vertically with the new coordinates of the center blocks.
So I had to narrow down the retry button.
Before:
After:
#33